Skip to content

Update setuptools to v75#1936

Merged
climbfuji merged 1 commit intoJCSDA:developfrom
eap:feature/setuptools-version-fix
Feb 27, 2026
Merged

Update setuptools to v75#1936
climbfuji merged 1 commit intoJCSDA:developfrom
eap:feature/setuptools-version-fix

Conversation

@eap
Copy link
Collaborator

@eap eap commented Feb 26, 2026

This change updates our pinned setuptools version to v75. This change is necessary due to the update to py-awscrt here spack/spack-packages#3553 which now requires setuptools >= v71.

Issues addressed

This change is part of the resolution to #1932

Applications affected

ewok-env

Systems affected

ec2, jedi-ci

Checklist

  • This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.
  • N/A All necessary updates to the documentation (spack-stack wiki) will be made when this PR is merged

@climbfuji
Copy link
Collaborator

I am waiting for the CI tests - curious if we get any duplicates or version conflicts for any of the environments. Will approve if they all pass.

@eap
Copy link
Collaborator Author

eap commented Feb 26, 2026

I am waiting for the CI tests - curious if we get any duplicates or version conflicts for any of the environments. Will approve if they all pass.

Agreed - I will note that when I did this locally with the unified-dev environment I observed a multi-version concretization problem resulting inpy-netcdf4 splitting between 1.6.5 and 1.7.2, but pinning the version to 1.7 fixed the duplicates.

I wasn't sure if it was an artifact of my local setup and environment contamination or if it was real. I suppose CI will help with this.

@climbfuji
Copy link
Collaborator

I am waiting for the CI tests - curious if we get any duplicates or version conflicts for any of the environments. Will approve if they all pass.

Agreed - I will note that when I did this locally with the unified-dev environment I observed a multi-version concretization problem resulting inpy-netcdf4 splitting between 1.6.5 and 1.7.2, but pinning the version to 1.7 fixed the duplicates.

I wasn't sure if it was an artifact of my local setup and environment contamination or if it was real. I suppose CI will help with this.

We definitely want 1.7.2.

@climbfuji
Copy link
Collaborator

The two successful CI runs used py-netcdf4@1.7.2.

@climbfuji climbfuji enabled auto-merge (squash) February 26, 2026 23:22
@climbfuji climbfuji merged commit 6d67b12 into JCSDA:develop Feb 27, 2026
6 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in spack-stack-2.2.x (2026 Q?) Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants